Tracealyzer for RTX64 (3.6 and Later)

NOTE: This documentation is for Tracealyzer for RTX64 3.6 and later. If you are using an earlier version of RTX64, you’ll want to see the documentation for Tracealyzer for RTX64 3.5 and earlier.

---

Tracealyzer's diagnostic capabilities allow you to trace application behavior in monitoring session data to see elements in your application that require optimization. For instance, Tracealyzer might reveal unnecessary resource conflicts in an application, which, when optimized, could result in a significant improvement in real-time responsiveness and performance.

Tracealyzer provides more than 30 interlinked views of application behavior, including scheduling and timing, interrupts, and interaction between threads and user events generated from your application. Tracealyzer can be used side-by-side with traditional debugging tools, and complements the debugger view with a higher level perspective, which is ideal for understanding more complex errors, such as race conditions, that cannot be analyzed through a typical debugging session.

There are several ways of accessing and arranging these views. The most frequently used views are found in the Navigation Bar.

The default Tracealyzer window layout with a session loaded

Tracealyzer contains several advanced analysis that help you to quickly comprehend the monitor data. For instance, it connects related monitor events, which allows you to follow activity between threads and to find the monitor event that triggers a particular thread instance. Moreover, it provides various higher-level views, such as the Communication Flow graph and the CPU Load Graphs, which make it easier to find anomalies in a monitoring session.